feat(runway): use singular Change on MergeStep instead of repeated#442
Merged
Conversation
Each MergeStep now carries a single Change (which itself holds multiple URIs) instead of a repeated list of Changes. This mirrors the SubmitQueue entity model where a Request has one Change containing all related URIs (e.g. stacked PRs).
kevinlnew
marked this pull request as ready for review
July 24, 2026 20:55
kevinlnew
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
July 24, 2026 20:55
behinddwalls
approved these changes
Jul 24, 2026
behinddwalls
temporarily deployed
to
stack-rebase
July 24, 2026 21:04 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Each MergeStep now carries a single Change (which itself holds multiple
URIs) instead of a repeated list of Changes. This mirrors the
SubmitQueue entity model where a Request has one Change containing all
related URIs (e.g. stacked PRs).